** Potential development goals **

1. "Newspeaters" -- APRS Digipeaters that also record QRPBBB packets and can
produce A:nnounce, S:ending, and W:anted packets, without needing a newsserver.
I'm thinking hardware like the STM32F429I (2MB Flash, 256kB RAM) evaluation
boards could handle it easily-- there's already stm32-digipeater code out there
to work from. A reason I've avoided 'complicated' enhancements (strong FEC,
etc.) is to keep it available to small CPUs in this situtation.

1a. Following-on from the minimum-CPU allowances, a Commodore 64 station. :)

2. Extending the S: command to handle multiple line payloads-- in an effort to
speed-up sending of header lines, while still preventing lines from being too
long, and not overly complicating the code.

One idea :-
    {{QS:462688b8,9#:Subject: Re: qrpbbb testing#10:From: vk2cjb@stoat.radio

Here, "9#" gives the line number and the seperator character (chosen to not
occur in the text), followed by the line, then the "#10" for the continuation line.

3. Allowing posts in certain newsgroups to be automatically acted upon by the
receiving sites, allowing remote commands like:

    Filter Callsign:VK6* EmailReply vk2cjb+survey@foo.net 'propagation survey'
    Filter Grid:PF95 EmailReply vk2cjb+survey@foo.net 'propagation survey'
    Filter Radius:>500,-32.3,151.4 EmailReply vk2cjb+survey@foo.net 'propagation survey'

One thought on this is to create a new Control: message command by adding a
script to /usr/lib/news/control/

3b. In aid of QSO'ing activity for contests and the like, have a specification
for manually acted on messages. (And what would be the impact of a lot of sites
all sending a message and replies on the same day..?)

4. The F:orget command

5. Have everything be more sensible (& tidier) with their output wrt cron usage.

6. Logging and Measurement improvements for determining the state of the local
APRS net and to use as feedback on channel congestion -- how many tx didn't get
an echo, how many wants were required, etc.

7. 'Incremental messages' with special msgids - for sending telemetry a line at
a time in a reliably distributed way, where the final msgid/checksum won't be
known.

8. qrpbbb_sharpack.py <args> - generates a single-file python script with
selected articles for transmitting via other means (EasyPAL, etc.) When that
script is executed, it lists the articles it contains, checks if already known,
and injects the articles.

9. Status reports -- from the last N hours, list the amount of traffic,
completed articles received (+ timestamp), incomplete articles. For use by
users checking for new messages..

10. Have ident/commands respond with a re-rerolled path route rather than
WIDEn-n.

